Suggest g_signal_connect (..., "realize", ...) instead of
authorRay Strode <rstrode@redhat.com>
Fri, 14 Dec 2007 17:06:08 +0000 (17:06 +0000)
committerRay Strode <halfline@src.gnome.org>
Fri, 14 Dec 2007 17:06:08 +0000 (17:06 +0000)
2007-12-14  Ray Strode  <rstrode@redhat.com>

* gtk/gtkwidget.c: Suggest g_signal_connect (..., "realize", ...)
instead of g_signal_connect_after (..., "realize", ...) as an
alternative to gtk_widget_realize () (bug 503537).

svn path=/trunk/; revision=19181

ChangeLog
gtk/gtkwidget.c

index dfca93aed235b4c287c1062cee689b10517902e9..d908dc1f8a13363c6076a53ee51a3ddf74d53f25 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2007-12-14  Ray Strode  <rstrode@redhat.com>
+
+       * gtk/gtkwidget.c: Suggest g_signal_connect (..., "realize", ...)
+       instead of g_signal_connect_after (..., "realize", ...) as an
+       alternative to gtk_widget_realize () (bug 503537).
+
 2007-12-14  Michael Natterer  <mitch@imendio.com>
 
        * gdk/gdkinternals.h
index b457e51ed5ade5810deb3775cadcd5d23e721103..faaa7d600a5034d45675991df7c34a99618b91cf 100644 (file)
@@ -3225,7 +3225,7 @@ gtk_widget_set_extension_events_internal (GtkWidget        *widget,
  * isn't very useful otherwise. Many times when you think you might
  * need it, a better approach is to connect to a signal that will be
  * called after the widget is realized automatically, such as
- * GtkWidget::expose-event. Or simply g_signal_connect_after() to the
+ * GtkWidget::expose-event. Or simply g_signal_connect () to the
  * GtkWidget::realize signal.
  **/
 void